Skip to content

chore: Update CODEOWNERS#28910

Merged
keithwillcode merged 1 commit intomainfrom
chore/remove-code-owners
Apr 15, 2026
Merged

chore: Update CODEOWNERS#28910
keithwillcode merged 1 commit intomainfrom
chore/remove-code-owners

Conversation

@keithwillcode
Copy link
Copy Markdown
Contributor

@keithwillcode keithwillcode commented Apr 15, 2026

What does this PR do?

Removed CODEOWNERS and leaving blank slate for new maintainers to use if desired

How should this be tested?

  • Are there environment variables that should be set?
  • What are the minimal test data to have?
  • What is expected (happy path) to have (input and output)?
  • Any other important info that could help to test that PR

Checklist

  • I haven't read the contributing guide
  • My code doesn't follow the style guidelines of this project
  • I haven't commented my code, particularly in hard-to-understand areas
  • I haven't checked if my changes generate no new warnings
  • My PR is too large (>500 lines or >10 files) and should be split into smaller PRs

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Apr 15, 2026

Welcome to Cal.diy, @keithwillcode! Thanks for opening this pull request.

A few things to keep in mind:

  • This is Cal.diy, not Cal.com. Cal.diy is a community-driven, fully open-source fork of Cal.com licensed under MIT. Your changes here will be part of Cal.diy — they will not be deployed to the Cal.com production app.
  • Please review our Contributing Guidelines if you haven't already.
  • Make sure your PR title follows the Conventional Commits format.

A maintainer will review your PR soon. Thanks for contributing!

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Apr 15, 2026

Hey there and thank you for opening this pull request! 👋🏼

We require pull request titles to follow the Conventional Commits specification and it looks like your proposed title needs to be adjusted.

Details:

No release type found in pull request title "Update CODEOWNERS". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:
 - feat: A new feature
 - fix: A bug fix
 - docs: Documentation only changes
 - style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
 - refactor: A code change that neither fixes a bug nor adds a feature
 - perf: A code change that improves performance
 - test: Adding missing tests or correcting existing tests
 - build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
 - ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
 - chore: Other changes that don't modify src or test files
 - revert: Reverts a previous commit

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Apr 15, 2026 •
edited
Loading

📝 Walkthrough

Walkthrough

The .github/CODEOWNERS file has been emptied, removing all 46 lines of path-to-team ownership mappings and exclusion patterns. This file previously defined code ownership assignments across multiple path categories including workflows, actions, apps, deploy, packages, and TypeScript/TSX/JSON files. The comment header and all test file pattern exclusions have also been removed.

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
Title check ❓ Inconclusive The title 'chore: Update CODEOWNERS' is vague and doesn't convey the actual intent—the PR removes all CODEOWNERS entries, not merely updates them. Consider a more descriptive title like 'chore: Clear CODEOWNERS file' or 'chore: Remove CODEOWNERS entries' to accurately reflect that the file is being emptied rather than updated.
✅ Passed checks (2 passed)
Check name Status Explanation
Description check ✅ Passed The description clearly explains the PR intent: removing the CODEOWNERS file to provide a blank slate for new maintainers, which directly relates to the changeset.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/remove-code-owners

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@keithwillcode keithwillcode changed the title Update CODEOWNERS chore: Update CODEOWNERS Apr 15, 2026
@keithwillcode keithwillcode merged commit f86e255 into main Apr 15, 2026
48 of 50 checks passed
@keithwillcode keithwillcode deleted the chore/remove-code-owners branch April 15, 2026 14:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@sahitya-chandra sahitya-chandra sahitya-chandra approved these changes

Assignees

No one assigned

Labels

ready-for-e2e size/M

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@keithwillcode @sahitya-chandra